Performance monitoring for storage system with core thread comprising internal and external schedulers

ABSTRACT

A processing device monitors performance of a first thread of a first application executing on one of a plurality of processing cores of a storage system. The first thread comprises an internal scheduler controlling switching between a plurality of sub-threads of the first thread, and an external scheduler controlling release of the processing core by the first thread for use by at least a second thread of a second application different than the first application. In conjunction with monitoring the performance of the first thread in executing the first application, the processing device maintains a cumulative suspend time of the first thread over multiple suspensions of the first thread, with one or more of the multiple suspensions allowing at least the second thread of the second application to execute on the processing core, and generates performance measurements for sub-threads of the first thread using the cumulative suspend time.

FIELD

The field relates generally to information processing systems, and moreparticularly to storage in information processing systems.

BACKGROUND

Information processing systems often include distributed storage systemscomprising multiple nodes. Nodes of a distributed storage system mayeach include multi-core processors that are configured to executethreads associated with various applications. One or more processingcores of a given such multi-core processor illustratively execute thethreads associated with a particular application. In some instances, anapplication may utilize an always-polling model in which threadsexecuting on one or more processing cores poll interfaces of theinformation processing system for new tasks, events, or other data. Inother instances, an application may use an event-driven model in whichinterrupts are used to activate threads for processing a task, event orother data using the one or more processing cores. Performancemonitoring techniques are typically used to monitor the performance ofsuch core threads in these and other contexts, but in some casesinaccurate measurements can result when a given processing core is usedto execute multiple threads of different applications.

SUMMARY

Illustrative embodiments provide performance monitoring techniques forstorage systems with core threads each comprising internal and externalschedulers. Such arrangements can provide substantially improvedperformance measurement accuracy in situations in which a givenprocessing core of a storage system is used to execute multiple threadsof different applications. For example, some embodiments areadvantageously configured to generate highly accurate performancemeasurements for respective sub-threads of a given thread of a primarystorage application executing on a processing core, even in situationsin which that thread is repeatedly suspended in order to allow one ormore threads of one or more other applications to execute on the sameprocessing core.

In one embodiment, at least one processing device comprises a processorcoupled to a memory, and is configured to monitor performance of a firstthread of a first application executing on one of a plurality ofprocessing cores of a storage system. The first thread comprises aninternal scheduler configured to control switching between a pluralityof sub-threads of the first thread, and an external scheduler configuredto control release of the processing core by the first thread for use byat least a second thread of a second application different than thefirst application. In conjunction with monitoring the performance of thefirst thread in executing the first application, the processing devicemaintains a cumulative suspend time of the first thread over multiplesuspensions of the first thread, with one or more of the multiplesuspensions allowing at least the second thread of the secondapplication to execute on the processing core. The processing devicegenerates performance measurements for respective ones of thesub-threads of the first thread based at least in part on the cumulativesuspend time of the first thread. The processing device in someembodiments comprises at least a subset of the plurality of processingcores of the storage system, although other arrangements are possible.

The first and second applications in some embodiments compriserespective block-storage and file-storage applications of the storagesystem. Additional or alternative applications can be used in otherembodiments.

The first thread in some embodiments comprises a truck thread that whenexecuting on the processing core is configured to utilize substantiallyall available processing resources of the processing core, although itis to be appreciated that other types of threads can be used as thefirst thread in other embodiments.

Each of the sub-threads of the first thread is illustratively in one ofmultiple designated states at a particular point in time, such as, forexample, a running state, a ready state and a suspended state.

In some embodiments, the sub-threads comprise respective non-preemptivethreads and the first thread is configured such that no sub-thread inthe running state is suspended to allow release of the processing coreby the first thread for use by the second thread. Instead, the multiplesuspensions of the first thread each occur in conjunction with a switchbetween sub-threads of the first thread.

In generating performance measurements for respective ones of thesub-threads of the first thread based at least in part on the cumulativesuspend time of the first thread, some embodiments generate a ready timemeasurement for a particular one of the sub-threads, and adjust theready time measurement based at least in part on the cumulative suspendtime of the first thread, with the adjusted ready time measurement beingindicative of an amount of time the sub-thread spent in the ready statewhile the first thread was not suspended. Similarly, some embodimentsgenerate a suspend time measurement for a particular one of thesub-threads, and adjust the suspend time measurement based at least inpart on the cumulative suspend time of the first thread, with theadjusted suspend time measurement being indicative of an amount of timethe sub-thread spent in the suspended state while the first thread wasnot suspended. Other types of measurements can be generated in otherembodiments.

In some embodiments, maintaining a cumulative suspend time of the firstthread over multiple suspensions of the first thread comprises, for eachof the multiple suspensions of the first thread, taking a firsttimestamp to indicate start of the suspension, taking a second timestampto indicate resumption of the first thread from the suspension, andadding a time interval corresponding to a difference between the firstand second timestamps to the cumulative suspend time.

Additionally or alternatively, maintaining a cumulative suspend time ofthe first thread over multiple suspensions of the first thread in someembodiments comprises, for each of the multiple suspensions of the firstthread, storing a current value of the cumulative suspend time inassociation with a current value of a suspension number counter that isincremented with each of the multiple suspensions of the first thread.

In some embodiments, generating performance measurements for respectiveones of the sub-threads of the first thread based at least in part onthe cumulative suspend time of the first thread comprises taking a firsttimestamp to indicate start of a performance interval, storing astarting value of the suspension number counter in conjunction withtaking the first timestamp, taking a second timestamp to indicate end ofthe performance interval, storing an ending value of the suspensionnumber counter in conjunction with taking the second timestamp,utilizing the starting and ending values of the suspension numbercounter to determine respective corresponding values of the cumulativesuspend time of the first thread, and adjusting a difference between thefirst and second timestamps based at least in part on a differencebetween the corresponding values of the cumulative suspend time of thefirst thread.

These and other illustrative embodiments include, without limitation,apparatus, systems, methods and processor-readable storage media.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an information processing system comprisinga storage system configured with performance monitoring functionalityfor a core thread with internal and external schedulers in anillustrative embodiment.

FIG. 2 is a block diagram of a processing device of the informationprocessing system of FIG. 1 comprising a plurality of processing coreseach executing a truck thread with internal and external schedulers inan illustrative embodiment.

FIGS. 3A and 3B are flow diagrams of different portions of an exampleperformance monitoring process for a core thread with internal andexternal schedulers in an illustrative embodiment. These figures arecollectively referred to herein as FIG. 3.

FIG. 4 shows example pseudocode for portions of a core thread withinternal and external schedulers in an illustrative embodiment.

FIG. 5 shows a performance monitoring example involving block-storageand file-storage applications running on a processing core in anillustrative embodiment.

FIG. 6 shows a content addressable storage system having a distributedstorage controller configured for implementing performance monitoringfunctionality for a core thread with internal and external schedulers inan illustrative embodiment.

FIGS. 7 and 8 show examples of processing platforms that may be utilizedto implement at least a portion of an information processing system inillustrative embodiments.

DETAILED DESCRIPTION

Illustrative embodiments will be described herein with reference toexemplary information processing systems and associated computers,servers, storage devices and other processing devices. It is to beappreciated, however, that these and other embodiments are notrestricted to the particular illustrative system and deviceconfigurations shown. Accordingly, the term “information processingsystem” as used herein is intended to be broadly construed, so as toencompass, for example, processing systems comprising cloud computingand storage systems, as well as other types of processing systemscomprising various combinations of physical and virtual processingresources. An information processing system may therefore comprise, forexample, at least one data center or other cloud-based system thatincludes one or more clouds hosting multiple tenants that share cloudresources. Numerous different types of enterprise computing and storagesystems are also encompassed by the term “information processing system”as that term is broadly used herein.

FIG. 1 shows an information processing system 100 configured inaccordance with an illustrative embodiment. The information processingsystem 100 comprises a computer system 101 that includes host devices102-1, 102-2, . . . 102-N, collectively referred to herein as hostdevices 102. The host devices 102 communicate over a network 104 with astorage system 105. The computer system 101 is assumed to comprise anenterprise computer system, cloud-based computer system or otherarrangement of multiple compute nodes associated with respective users.The host devices 102 of the computer system 101 in some embodimentsillustratively provide compute services such as execution of one or moreapplications on behalf of each of one or more users associated withrespective ones of the host devices 102. Such applicationsillustratively generate input-output (10) operations that are processedby the storage system 105. The term “input-output” as used herein refersto at least one of input and output. For example, IO operations maycomprise write requests and/or read requests directed to logicaladdresses of a particular logical storage volume of the storage system105. These and other types of IO operations are also generally referredto herein as IO requests.

The host devices 102 and storage system 105 illustratively compriserespective processing devices of one or more processing platforms. Forexample, the host devices 102 and the storage system 105 can eachcomprise one or more processing devices each comprising a processor anda memory, possibly implementing virtual machines and/or containers,although numerous other configurations are possible.

The host devices 102 and the storage system 105 can additionally oralternatively be part of cloud infrastructure such as an Amazon WebServices (AWS) system. Other examples of cloud-based systems that can beused to provide one or more of host devices 102 and storage system 105include Google Cloud Platform (GCP) and Microsoft Azure.

The host devices 102 and the storage system 105 may be implemented on acommon processing platform, or on separate processing platforms.

The host devices 102 are configured to write data to and read data fromthe storage system 105 in accordance with applications executing onthose host devices 102 for system users.

The term “user” herein is intended to be broadly construed so as toencompass numerous arrangements of human, hardware, software or firmwareentities, as well as combinations of such entities. Compute and/orstorage services may be provided for users under a Platform-as-a-Service(PaaS) model, an Infrastructure-as-a-Service (IaaS) model and/or aFunction-as-a-Service (FaaS) model, although it is to be appreciatedthat numerous other cloud infrastructure arrangements could be used.Also, illustrative embodiments can be implemented outside of the cloudinfrastructure context, as in the case of a stand-alone computing andstorage system implemented within a given enterprise.

The network 104 is assumed to comprise a portion of a global computernetwork such as the Internet, although other types of networks can bepart of the network 104, including a wide area network (WAN), a localarea network (LAN), a satellite network, a telephone or cable network, acellular network such as a 4G or 5G network, a wireless network such asa WiFi or WiMAX network, or various portions or combinations of theseand other types of networks. The network 104 in some embodimentstherefore comprises combinations of multiple different types of networkseach comprising processing devices configured to communicate usingInternet Protocol (IP) or other communication protocols.

As a more particular example, some embodiments may utilize one or morehigh-speed local networks in which associated processing devicescommunicate with one another utilizing Peripheral Component Interconnectexpress (PCIe) cards of those devices, and networking protocols such asInfiniBand, Gigabit Ethernet or Fibre Channel. Numerous alternativenetworking arrangements are possible in a given embodiment, as will beappreciated by those skilled in the art.

The storage system 105 is accessible to the host devices 102 over thenetwork 104. The storage system 105 comprises a plurality of nodes106-1, 106-2, . . . 106-M, collectively referred to herein as nodes 106.The storage system 105 comprising nodes 106 is an example of what isalso referred to herein as a “distributed storage system” or a“clustered storage system.” For example, in some implementations ofstorage system 105, the nodes 106 are interconnected in a full meshnetwork, such that each of the nodes 106 can communicate with each ofthe other nodes 106, although other types of networks and different nodeinterconnection arrangements can be used in other embodiments. At leastportions of respective ones of the nodes 106 illustratively implementwhat is generally referred to herein as a “distributed storagecontroller” of the storage system 105.

In the FIG. 1 embodiment, the nodes 106-1, 106-2, . . . 106-M of thestorage system 105 comprise respective processing devices 108-1, 108-2,. . . 108-M, collectively referred to herein as processing devices 108.One or more of the nodes 106 may each comprise multiple processingdevices 108, although only single instances of such processing devicesare shown in the figure. In some embodiments, multiple processingdevices 108 of a given one of the nodes 106 may act or function as asingle processing device 108.

The processing devices 108-1, 108-2, . . . 108-M comprise respectivesets of cores 110-1, 110-2, . . . 110-M, collectively referred to hereinas cores 110. For example, a given processing device 108 may comprise aset of two cores 110, four cores 110, eight cores 110, or any othernumber of cores 110 appropriate to a given implementation. Theprocessing devices 108 therefore each illustratively comprise amulti-core processor and associated memory.

The nodes 106-1, 106-2, . . . 106-M further comprise respective sets ofstorage devices 112-1, 112-2, . . . 112-M, collectively referred toherein as storage devices 112. For example, a given one of the nodes 106may comprise a single storage device 112, two storage devices 112, fourstorage devices 112, eight storage devices 112, sixteen storage devices112, thirty-two storage devices 112 or any other number of storagedevices 112. The storage devices 112-1, 112-2, . . . 112-M storerespective datasets 114-1, 114-2, . . . 114-M, collectively referred toherein as datasets 114, which illustratively comprise logical units(LUNs) or other types of logical storage volumes, as well as snapshotsand/or other arrangements of data, possibly including associatedmetadata, as in an embodiment in which storage devices 112 store userdata pages and metadata pages of LUNs or other logical storage volumes.

The storage devices 112 of the storage system 105 illustrativelycomprise solid state drives (SSDs). Such SSDs are implemented usingnon-volatile memory (NVM) devices such as flash memory. Other types ofNVM devices that can be used to implement at least a portion of thestorage devices 112 include non-volatile random access memory (NVRAM),phase-change RAM

(PC-RAM), magnetic RAM (MRAM), resistive RAM, spin torque transfermagneto-resistive RAM (STT-MRAM), and Intel Optane™ devices based on 3DXPoint™ memory. These and various combinations of multiple differenttypes of NVM devices may also be used. For example, hard disk drives(HDDs) can be used in combination with or in place of SSDs or othertypes of NVM devices.

However, it is to be appreciated that other types of storage devices canbe used in storage system 105 in other embodiments. For example, a givenstorage system as the term is broadly used herein can include acombination of different types of storage devices, as in the case of amulti-tier storage system comprising a flash-based fast tier and adisk-based capacity tier. In such an embodiment, each of the fast tierand the capacity tier of the multi-tier storage system comprises aplurality of storage devices with different types of storage devicesbeing used in different ones of the storage tiers. For example, the fasttier may comprise flash drives while the capacity tier comprises harddisk drives. The particular storage devices used in a given storage tiermay be varied in other embodiments, and multiple distinct storage devicetypes may be used within a single storage tier. The term “storagedevice” as used herein is intended to be broadly construed, so as toencompass, for example, SSDs, HDDs, flash drives, hybrid drives or othertypes of storage devices.

In some embodiments, the storage system 105 illustratively comprises ascale-out all-flash content addressable storage array such as anXtremIO™ storage array from Dell EMC of Hopkinton, Mass. A wide varietyof other types of storage arrays can be used in implementing the storagesystem 105 in other embodiments, including by way of example one or moreVNX®, VMAX®, Unity™ or PowerMax™ storage arrays, each commerciallyavailable from Dell EMC.

Additional or alternative types of storage products that can be used inimplementing a given storage system in illustrative embodiments include,by way of example, software-defined storage, cloud storage, object-basedstorage and scale-out storage. Combinations of multiple ones of theseand other storage types can also be used in implementing a given storagesystem in an illustrative embodiment.

The term “storage system” as used herein is therefore intended to bebroadly construed, and should not be viewed as being limited to storagesystems based on flash memory or other types of NVM storage devices. Agiven storage system as the term is broadly used herein can comprise,for example, network-attached storage (NAS), storage area networks(SANs), direct-attached storage (DAS) and distributed DAS, as well ascombinations of these and other storage types, includingsoftware-defined storage.

The storage system 105 should also be understood to include additionalmodules and other components typically found in conventionalimplementations of storage systems, although such additional modules andother components are omitted from the figure for clarity and simplicityof illustration.

In some embodiments, communications between the host devices 102 and thestorage system 105 comprise Small Computer System Interface (SCSI) orInternet SCSI (iSCSI) commands. Other types of SCSI or non-SCSI commandsmay be used in other embodiments, including commands that are part of astandard command set, or custom commands such as a “vendor uniquecommand” or VU command that is not part of a standard command set. Theterm “command” as used herein is therefore intended to be broadlyconstrued, so as to encompass, for example, a composite command thatcomprises a combination of multiple individual commands. Numerous othercommands can be used in other embodiments.

For example, although in some embodiments certain commands used by thehost devices 102 to communicate with the storage system 105illustratively comprise SCSI or iSCSI commands, other embodiments canimplement IO operations utilizing command features and functionalityassociated with NVM Express (NVMe), as described in the NVMeSpecification, Revision 1.3, May 2017, which is incorporated byreference herein. Other storage protocols of this type that may beutilized in illustrative embodiments disclosed herein include NVMe overFabric, also referred to as NVMeoF, and NVMe over Transmission ControlProtocol (TCP), also referred to as NVMe/TCP.

As indicated previously, the host devices 102 and the storage system 105may be implemented on respective distinct processing platforms, althoughnumerous other arrangements are possible. For example, in someembodiments at least portions of the host devices 102 and the storagesystem 105 are implemented on the same processing platform. The storagesystem 105 can therefore be implemented at least in part within at leastone processing platform that implements at least a portion of the hostdevices 102. In the FIG. 1 embodiment, storage system 105 is implementedas a distributed or clustered storage system comprising nodes 106 thatmay be logically or physically distributed.

The term “processing platform” as used herein is intended to be broadlyconstrued so as to encompass, by way of illustration and withoutlimitation, multiple sets of processing devices and associated storagesystems that are configured to communicate over one or more networks.For example, distributed implementations of the system 100 are possible,in which certain components of the system reside in one data center in afirst geographic location while other components of the system reside inone or more other data centers in one or more other geographic locationsthat are potentially remote from the first geographic location. Thus, itis possible in some implementations of the system 100 for the hostdevices 102 and storage system 105 to reside in different data centers.Numerous other distributed implementations of one or both of the hostdevices 102 and the storage system 105 are possible. Accordingly, thestorage system 105 can also be implemented in a distributed manneracross multiple data centers.

Additional examples of processing platforms utilized to implement hostdevices and/or storage systems in illustrative embodiments will bedescribed in more detail below in conjunction with FIGS. 7 and 8.

It is to be appreciated that the above-described features and otherfeatures of illustrative embodiments disclosed herein are presented byway of example only and should not be construed as limiting in any way.

The particular sets of modules and other components implemented in thesystem 100 as illustrated in FIG. 1 are therefore presented by way ofillustrative example only. In other embodiments, only subsets of thesecomponents, or additional or alternative sets of components, may beused, and such components may exhibit alternative functionality andconfigurations. Accordingly, different numbers, types and arrangementsof system components such as host devices 102, network 104, storagesystem 105, nodes 106, processing devices 108, cores 110, storagedevices 112, and datasets 114, or additional or alternative components,can be used in other embodiments.

Also, in some embodiments, the core thread performance monitoringfunctionality described herein can be implemented at least in part inone or more host devices, or partially in a host device and partially ina storage system. Accordingly, illustrative embodiments are not limitedto arrangements in which all such functionality is implemented in astorage system, and therefore encompass various hybrid arrangements inwhich the functionality is distributed over one or more storage systemsand one or more associated host devices, each comprising one or moreprocessing devices.

Referring now to FIG. 2, a given one of the processing devices 108,denoted as processing device 108-i, where i=1, 2, . . . M, is shown inmore detail. The processing device 108-i in this embodiment comprises amulti-core processor including processing cores 210-0, 210-1, . . .210-P. The processing core 210-0 implements a system manager 216 and aperformance monitor 218. The other processing cores 210-1 through 210-Pexecute respective truck threads 224-1 through 224-P, comprisingrespective sets of multiple sub-threads illustratively in the form ofX-threads 225-1 through 225-P. Other types of sub-threads can be used inother embodiments. The processing cores 210-1 through 210-P also executerespective sets of one or more other application threads 226-1 through226-P. These and other threads illustratively comprise operating system(OS) threads of their respective cores 210.

For example, in the case of a block-storage application, which handlesthe block-based storage functionality of the storage system 105, theblock-storage application executes truck threads 224 on respective onesof the cores 210 of the processing device 108-i. These truck threads 224implement the block-storage application functionality. In someembodiments, each of the truck threads 224 may be hard affined to aparticular one of the processing cores 210, such that it may onlyexecute on that particular core.

The processing cores 210 in some embodiments illustratively compriserespective distinct central processing units (CPUs). Accordingly, eachof the processing devices 108 of the respective nodes 106 of storagesystem 105 may be viewed as comprising a multi-core CPU and anassociated storage array comprising a set of storage devices 112,although numerous other arrangements are possible. The storage array orother arrangement of storage devices 112 associated with a given one ofthe nodes 106 may comprise, for example, a disk array enclosure (DAE),although such references herein to “disks” should not be construed as anindication that the storage devices are limited to HDDs or otherrotating magnetic storage media.

The above-noted multi-core CPU illustratively runs the block-storageapplication on top of a preemptive OS, where a preemptive OS can preempt(e.g., stop) a running OS thread without its cooperation, and executesomething else, such as another OS thread. The block-storage applicationis illustratively running a single hard-affined OS thread per each CPUcore, which implements the block-storage functionality. This OS threadis an example of what is also referred to herein as a “truck thread.”Truck threads and other application threads running on a given CPU coreor other processing core are more generally referred to herein as “corethreads” of that processing core.

As part of its operation, each of the truck threads 224 polls acorresponding set of interfaces of the storage system 105 for tasks,events, or other data to be processed by that truck thread. For example,the set of interfaces may include an interface for indications ofcompletions of submitted IO requests, an interface for IO requests fromthe user, and interfaces for other tasks, events, or other data. Anyother interfaces may also be polled. Each truck thread, by design, fullyutilizes the processing core that it is executing on for both interfacepolling and processing of the corresponding tasks, events, or otherdata. For example, in illustrative embodiments, each truck thread isdesigned to fully utilize the processing core that it is executing onbecause, even when there is no actual processing of tasks to beperformed, the truck thread continues checking its respective interfacesvia polling. This design is optimized for a storage system that requireslow latency and high IO operations per second (IOPS) since no contextswitches or interrupts are required to perform the processing. In someembodiments, the functionality of the block-storage application may bedescribed as an always-polling model.

In some embodiments, example interfaces that may be polled by a truckthread may include a front-end interface, a remote procedure call (RPC)messaging interface, a remote direct memory access (RDMA) messaginginterface, and a back-end interface. In some embodiments, any otherinterface commonly used in a storage system may also be polled by thetruck thread. In some embodiments, each truck thread defines anIO-provider instance for each corresponding interface that it isresponsible for polling.

The front-end interface illustratively comprises an interface forreceiving and replying to IO requests from users of the storage system105 associated with respective ones of the host devices 102. Forexample, a given truck thread may comprise a front-end IO-providerinstance that polls for new IO requests from one or more host devices102 or other system users. In some embodiments, for example, IO requestsreceived by the storage system 105 from the user are pooled together ina common pool that is shared between the truck threads 224 and accessedusing a front-end IO-provider instance.

The RPC messaging interface illustratively comprises an interface forsending and receiving messages to and from other nodes 106 of thestorage system 105. For example, a given truck thread may comprise anRPC messaging IO-provider that polls for new messages from other nodes106 in the storage system 105. As an example, when one of the nodes 106sends an IO request to another one of the nodes 106, the sender nodeselects the specific destination truck thread, that is, the truck threadthat will receive and handle the request.

The RDMA messaging interface illustratively comprises an interface forRDMA transfer of buffers between nodes 106. For example, a given truckthread may comprise an RDMA messaging IO-provider that polls for thecompletion of RDMA transfers between nodes 106.

The back-end interface illustratively comprises an interface foraccessing the storage devices 112 in order to write data to and readdata from the storage devices 112. For example, a given truck thread maycomprise a back-end IO-provider that polls for the completion of writeand read requests initiated by the truck thread to one or more of thestorage devices 112 of processing device 108-i.

In some cases, the storage system 105 may also implement one or moreother applications aside from the block-storage application. Forexample, a file-storage application that provides a file interface to auser of the information processing system 100 may also be implemented bythe storage system 105, for example, by executing corresponding threads226 on one or more of the cores 210. In some cases, the block-storageapplication and the file-storage application, or any other application,may be implemented by the storage system 105 simultaneously, each with adifferent load that can dynamically change over time.

Since these applications are attempting to utilize the same set ofprocessing cores 210 simultaneously, management of the availableprocessing resources of these cores 210 between the applications can bechallenging. For example, since the block-storage application isimplemented by executing truck threads 224 on each of the processingcores 210 of each of the nodes 106, and these truck threads 224 canutilize the full capacity of those processing cores 210, little to noprocessing resources of the storage system 105 may be available for useby threads 226 of another application.

In some embodiments, if only the file-storage application is actively inuse, such that no tasks, events, or other data are present for the truckthreads 224 to process, the associated file threads may only be able toutilize a portion of the processing resources of a core, such as 50% oranother percentage, where the remaining portion, such as the other 50%or another percentage, will be used by the truck threads 224 just forpolling interfaces. In cases where the block-storage application isactively performing operations, the truck threads 224 will utilize asubstantial portion of the processing resources of the cores, such as90%, 95%, or even 100%, to both poll the interfaces and process anytasks, events, or other data found on those interfaces during thepolling, which leaves little to no processing resources available onthose cores for use by other applications such as a file-storageapplication.

Examples of storage systems that allow the full processing resources ofa core to be available for use by other applications, even when a truckthread of a block-storage application is utilizing that core to supportits functionality, are disclosed in U.S. patent application Ser. No.16/251,779, filed Jan. 18, 2019 and entitled “Multi-Core Processor inStorage System Executing Dedicated Polling Thread for Increased CoreAvailability,” which is incorporated by reference herein in itsentirety. This patent application more particularly discloses a storagesystem that in one or more illustrative embodiments is able todynamically adapt to the user operation patterns of multiplesimultaneously implemented applications where, for example, one of theapplications executes an always-polling model of functionality thatconsumes significant processing resources using the above-describedtruck threads.

Additionally, techniques are disclosed in the above-cited U.S. patentapplication Ser. No. 16/251,779 for creating an event-driven storagesystem out of a storage system implementing the above-describedalways-polling model, through the use of a dedicated peek-poller thread.The dedicated peek-poller thread serves as a mechanism to allow for thesharing of the full resources of the other cores in a processing devicebetween the two or more applications in a manner that dynamicallymatches the user operation pattern. For example, the dedicatedpeek-poller thread is executed on a core of the processing device andpartially replaces the polling functionality of each of the truckthreads executing on the other cores in the processing device, therebyfreeing up the processing resources of those other cores that wouldotherwise be used by the truck threads for polling for use by otherapplications during times when the block-storage application isexperiencing reduced activity.

However, a situation may arise where, for example, the block-storageapplication is utilizing the full resources of the processing cores 210such that having a dedicated peek-poller thread executing on one of thecores 210 reduces the total amount of processing resources available tothe block-storage application. For example, if there are ten coresavailable on the processing device 108-i, and one of the cores isexecuting a dedicated peek-poller thread, only nine of the cores or 90%of the processing resources of the processing device are available foruse by the block-storage application.

U.S. patent application Ser. No. 16/251,868, filed Jan. 18, 2019 andentitled “Multi-Core Processor in Storage System Executing DynamicThread for Increased Core Availability,” also incorporated by referenceherein in its entirety, discloses in illustrative embodiments dynamictruck threads that may be executed on the cores of a processing device.The function of each of the dynamic truck threads is modifiable betweenmultiple operating modes such that the full processing resources of theall of the cores of a processing device are available for use by ablock-storage application during periods of time when the block-storageapplication is exhibiting high levels of core utilization while theprocessing resources of the cores are also available for otherapplications during periods of time when the block-storage applicationis exhibiting moderate to low levels of core utilization.

For example, in such embodiments, the function of a given dynamic truckthread is dynamically modifiable between an operating mode where thegiven dynamic truck thread performs the above-described truck threadfunctionality and an operating mode where the given dynamic truck threadperforms at least some of the above-described peek-poller threadfunctionality. In some embodiments, the functionality of each of thedynamic truck threads may also be modified to an operating mode whereall functions of the dynamic truck threads are disabled on the cores 210of the processing device 108-i such that the processing resources of thecores 210 are fully available for use by other applications, such as afile-storage application.

Illustrative embodiments disclosed herein can utilize one or more of thetechniques disclosed in the above-cited U.S. patent application Ser.Nos. 16/251,779 and 16/251,868. For example, one or more of the truckthreads 224 of FIG. 2 may be implemented as respective dynamic truckthreads. However, it is to be appreciated that utilization of suchtechniques is not required in illustrative embodiments disclosed herein.

The processing cores 210 of the FIG. 2 embodiment can therefore executethreads of multiple applications, including truck threads 224 and otherapplication threads 226. For example, in some embodiments, ablock-storage application is implemented by executing truck threads 224on respective ones of the cores 210, with each of the truck threads 224implementing a corresponding portion of the block-storage application.As described above, by executing truck threads 224 on respective cores210, a significant portion of the processing resources of each of thecores 210 is utilized for polling interfaces associated with itscorresponding truck thread, and processing associated tasks, events orother data found on those interfaces, leaving little to no processingresources available on that core for executing the threads of otherapplications. Some embodiments address this issue through the use ofdynamic truck threads executing on one or more of the processing cores210.

As indicated previously, performance monitoring techniques are typicallyused in a storage system to monitor the performance of core threads,such as the truck threads 224 executing on respective ones of theprocessing cores 210. Conventional performance monitoring techniques areproblematic in that they can generate inaccurate measurements when agiven processing core is used to execute multiple threads of differentapplications, such as the above-noted block-storage application andfile-storage application.

The storage system 105 is advantageously configured to avoid these andother drawbacks of conventional storage systems by providing enhancedperformance monitoring techniques that can generate significantly moreaccurate measurements in situations in which a given processing core ofa storage system is used to execute multiple threads of differentapplications. For example, some embodiments are advantageouslyconfigured to generate highly accurate performance measurements forrespective sub-threads of a given thread of a primary storageapplication executing on a processing core, even in situations in whichthat thread is repeatedly suspended in order to allow one or morethreads of one or more other applications to execute on the sameprocessing core.

In some embodiments, the processing device 108-i of the storage system105 is configured to implement performance monitoring functionality forcore threads of the storage system 105, such as the truck threads 224that include respective internal schedulers 230 and respective externalschedulers 232. Each of the other processing devices 108 is assumed tobe similarly configured. This core thread performance monitoringfunctionality of the processing device 108-i will now be described inmore detail.

In operation, the performance monitor 218 is configured to monitorperformance of threads executing on the processing cores 210, such astruck threads 224 and other application threads 226. Such performancemonitoring in illustrative embodiments involves collecting performancemeasurements from respective ones of the core threads.

For example, in the FIG. 2 embodiment, the truck thread 224-1 is assumedto be part of a block-storage application executing on the processingcore 210-1. The truck thread 224-1 comprises internal scheduler 230-1,illustratively configured to control switching between particular onesof the X-threads 225-1 of the truck thread 224-1, and external scheduler232-1, illustratively configured to control release of the processingcore 210-1 by the truck thread 224-1 for use by at least one of theother application threads 226-1 of a second application different thanthe block-storage application. In some embodiments, the secondapplication comprises a file-storage application, although referencesherein to block-storage applications and file-storage applications areconsidered non-limiting examples. It will be assumed for description ofillustrative embodiments below that the second application comprises afile-storage application that executes using one or more of the otherapplication threads 226 on one or more of the processing cores 210.

In conjunction with monitoring the performance of the truck thread 224-1in executing the block-storage application, a cumulative suspend time ofthe truck thread 224-1 is maintained over multiple suspensions of thetruck thread 224-1, where one or more of the multiple suspensions allowat least the other application thread 226-1 of the file-storageapplication to execute on the processing core 210-1, and performancemeasurements are generated for respective ones of the X-threads 225-1 ofthe truck thread 224-1 based at least in part on the cumulative suspendtime of the truck thread 224-1. Such operations are performed at leastin part by the external scheduler 232-1 of the truck thread 224-1.

The performance monitor 218 illustratively gathers such performancemeasurements from the truck thread 224-1 and from other ones of thetruck threads 224 executing on respective other ones of the cores 210,and provides such measurements to the system manager 216 for use incontrolling configuration of the processing device 108-i and itsprocessing cores 210 and their associated threads 224 and 226. Asmentioned previously, the truck thread 224-1 when executing on theprocessing core 210-1 is illustratively configured to utilizesubstantially all available processing resources of the processing core210-1, such as 90% or more of the available processing resources of thatcore. Other embodiments can combine at least portions of system manager216 and performance monitor 218 into a single component implemented onone or more processing cores 210 of at least one of the processingdevices 108.

As indicated above, the truck threads 224 run respective sets ofX-threads 225. The X-threads 225 illustratively comprise respectivelightweight threads that are scheduled by the internal schedulers 230 ofthe respective truck threads 224. For example, there may be thousands ofX-threads 225 associated with each of the truck threads 224. TheX-threads 225 in some embodiments are non-preemptive (e.g.,cooperative), which means that one of the X-threads of a particulartruck thread voluntarily gives up execution in order to allow anotherone of the X-threads of that truck thread to be scheduled. If anX-thread is doing a lengthy computational task (e.g., a task taking tensof microseconds), it should contain explicit yield and/or suspensioncalls, or implicit calls by waiting on synchronization objects.

It is assumed in some embodiments herein that each X-thread can be inone multiple designated states at a particular point in time, including,for example, a running state, a ready state and a suspended state. Inthe running state, the X-thread is currently running. In the suspendedstate, the X-thread is waiting on a synchronization object (e.g., asemaphore, timer, etc.) In the ready state, the X-thread is ready torun, but waiting for the processing core (e.g., another X-thread iscurrently running).

The X-threads 225-1 are examples of what are more generally referred toherein as “sub-threads” of their corresponding truck thread 224-1. Othertypes of sub-threads having different arrangements of possible statescan be used in other embodiments.

The X-threads 225-1 in some embodiments therefore comprise respectivenon-preemptive threads and the truck thread 224-1 is configured suchthat no X-thread in the running state is suspended to allow release ofthe processing core 210-1 by the truck thread 224-1 for use by the otherapplication thread 226-1. The above-noted multiple suspensions of thetruck thread 224-1 to allow the other application thread 226-1 toexecute therefore each occur in conjunction with a switch betweenX-threads 225-1 of the truck thread 224-1. As mentioned previously, thescheduling of the X-threads 225-1 is illustratively performed under thecontrol of the internal scheduler 230-1 of the truck thread 224-1.

In some embodiments, the external scheduler 232-1 of the truck thread224-1 comprises a processing core release component and a wakercomponent. The processing core release component is configured todetermine, in conjunction with each switch between X-threads 225-1 ofthe truck thread 224-1, whether or not the truck thread 224-1 willsuspend itself so as to release the processing core 210-1 for use by atleast another application thread 226-1 of the file-storage application.The processing core release component in some embodiments may bereferred to as a CPU release component, as the processing cores such ascores 210 may comprise respective distinct CPUs of the processing device108-i.

In some embodiments, the processing core release component of the truckthread 224-1 more particularly operates as follows. On every X-threadswitch, a determination is made as to whether or not the truck thread224-1 will give up execution, to allow other applications (e.g., afile-storage application) to run. When a truck thread suspends itself,it will resume execution when no other application is ready to run, orit will be rescheduled to run after a certain time by the wakercomponent, whichever happens first.

The waker component is configured to determine, in conjunction with eachswitch between X-threads 225-1 of the truck thread 224-1, whether or notthere is at least one additional thread of the block-storage applicationto be returned from suspension prior to release of the processing core210-1 by the truck thread 224-1.

The waker component in some embodiments more particularly operates asfollows. On every X-thread switch, and before the decision is madewhether to give up the processing core, the waker component checks ifthere are currently one or more other truck threads of the block-storageapplication that are suspended and need to be awakened, and if so itwakes up the one or more other truck threads.

The processing core release component therefore illustratively operatesin conjunction with the waker component to suspend the truck thread224-1 and to return the truck thread 224-1 from suspension. Otherarrangements of additional or alternative components can be included inthe external scheduler 232-1 in other embodiments.

Example sets of pseudocode for implementing at least a portions of theinternal scheduler 230-1 and the external scheduler 232-1 of the truckthread 224-1 will be described below in conjunction with FIG. 4.

In some embodiments, generating performance measurements for respectiveones of the X-threads 225-1 of the truck thread 224-1 based at least inpart on the cumulative suspend time of the truck thread 224-1 comprisesgenerating a ready time measurement for a particular one of theX-threads 225-1, and adjusting the ready time measurement based at leastin part on the cumulative suspend time of the truck thread 224-1. Theadjusted ready time measurement is indicative of an amount of time theparticular X-thread spent in the ready state while the truck thread224-1 was not suspended.

Additionally or alternatively, generating performance measurements forrespective ones of the X-threads 225-1 of the truck thread 224-1 basedat least in part on the cumulative suspend time of the truck thread224-1 comprises generating a suspend time measurement for a particularone of the X-threads 225-1, and adjusting the suspend time measurementbased at least in part on the cumulative suspend time of the truckthread 224-1. The adjusted suspend time measurement is indicative of anamount of time the particular X-thread spent in the suspended statewhile the truck thread 224-1 was not suspended.

The above-noted ready time measurement and suspend time measurement areexamples of “performance measurements” that are generated for respectiveones of the X-threads 225-1 of the truck thread 224-1 based at least inpart on the cumulative suspend time of the truck thread 224-1.

A wide variety of other types of performance measurements can begenerated in other embodiments, and the term “performance measurement”as used herein is therefore intended to be broadly construed. Suchperformance measurements are illustratively collected from the truckthread 224-1 and the other truck threads 224 by the performance monitor218, and utilized by system manager 216 in controlling configuration ofone or more of the processing cores 210 of the processing device 108-i.

In some embodiments, generation of performance measurements includeslogging of performance counters as triggered by scheduling events, suchas an X-thread state changing from the running state, to the suspendedstate, to the ready state. For example, the performance monitor 218 cancollect time “counters” or other time measurements per flow that measurevarious aspects of the flow operation, where a given flow in thiscontext illustratively corresponds to an X-thread. Performancemeasurements that can be made include the above-noted ready timemeasurement and suspend time measurement. The ready time measurementillustratively measures the amount of time a given flow was ready torun, but waiting for the core, and corresponds to the amount of time itsX-thread was in the ready state. Similarly, the suspend time measurementillustratively measures the amount of time the given flow was waiting onsome synchronization object, and corresponds to the amount of time itsX-thread was in the suspended state. The corresponding time intervalsfor the suspend time measurement are illustratively collected for eachsynchronization object that the given flow was waiting on during itsexecution. Other performance measurements include running timemeasurements, which measure the actual runtime of the given flow, andcorresponds to the amount of time that its X-thread was in the runningstate.

Illustrative embodiments herein recognize that the ready time andsuspend time measurements made for particular X-threads can be adverselyimpacted by not properly measuring amounts of time that thecorresponding truck thread was suspended to allow for execution of otherapplication threads on the same core. For example, during the ready timeand suspend time intervals described above, the truck thread 224-1executing the block-storage application may be suspended multiple times,leading to false measurements of these types of intervals. Moreparticularly, if during the time a flow of an X-thread is in the readystate and the truck thread 224-1 decides to perform a context switch soas to release the core for use by one or more other applications, thetime spent by the other application(s) will be added to the measurement,which is time outside the context of the block-storage application, andtherefore will not accurately reflect the internal ready or suspendtime, and may instead provide a significantly longer duration.Illustrative embodiments herein overcome such issues by maintaining acumulative suspend time for the truck thread 224-1, and generatingperformance measurements for a given one of the X-threads 225-1 of thattruck thread 224-1, such as the above-noted ready time and suspend timemeasurements, in an efficient manner that properly accounts for theamount of time that the truck thread 224-1 is suspended.

It should be noted in this regard that the running time measurement ofan X-thread is not similarly impacted by suspend time of its truckthread, as the external scheduler of the truck thread in illustrativeembodiments does not preempt X-threads, but instead suspends the truckthread only in conjunction with a switch between X-threads.

Additional performance monitoring functionality implemented in storagesystem 105 in some embodiments includes aspects of performancemonitoring as disclosed in U.S. Pat. No. 10,152,232, entitled“Low-Impact Application-Level Performance Monitoring with Minimal andAutomatically Upgradable Instrumentation in a Storage System,” which isincorporated by reference herein in its entirety.

For example, U.S. Pat. No. 10,152,232 describes techniques formonitoring of storage system processing time dynamics at a flow level,in order to generate performance measurements that can be used forvarious purposes such as for the investigation and debugging of issuesas well as for performance analysis of the storage system.

However, other performance monitoring techniques can be implemented inother embodiments, and illustrative embodiments should therefore not beviewed as being limited to use with any particular performancemonitoring techniques, such as those disclosed in U.S. Pat. No.10,152,232.

In some embodiments, maintaining a cumulative suspend time of the truckthread 224-1 over multiple suspensions of the truck thread 224-1comprises, for each of the multiple suspensions of the truck thread224-1, taking a first timestamp to indicate start of the suspension,taking a second timestamp to indicate resumption of the truck thread224-1 from the suspension, and adding a time interval corresponding to adifference between the first and second timestamps to the cumulativesuspend time.

Additionally or alternatively, maintaining a cumulative suspend time ofthe truck thread 224-1 over multiple suspensions of the truck thread224-1 comprises, for each of the multiple suspensions of the truckthread 224-1, storing a current value of the cumulative suspend time inassociation with a current value of a suspension number counter that isincremented with each of the multiple suspensions of the truck thread224-1.

Such operations are illustratively performed by the external scheduler232-1 of the truck thread 224-1. For example, these operations can beperformed by the processing core release component of the externalscheduler 232-1 of the truck thread 224-1.

In some embodiments, generating performance measurements for respectiveones of the X-threads 225-1 of the truck thread 224-1 based at least inpart on the cumulative suspend time of the truck thread 224-1 comprisestaking a first timestamp to indicate start of a performance interval,storing a starting value of the suspension number counter in conjunctionwith taking the first timestamp, taking a second timestamp to indicateend of the performance interval, storing an ending value of thesuspension number counter in conjunction with taking the secondtimestamp, utilizing the starting and ending values of the suspensionnumber counter to determine respective corresponding values of thecumulative suspend time of the truck thread 224-1, and adjusting adifference between the first and second timestamps based at least inpart on a difference between the corresponding values of the cumulativesuspend time of the truck thread 224-1. The resulting performancemeasurement is adjusted to account for an amount of time the particularX-thread spent in the suspended state while the truck thread 224-1 wasnot suspended. Like other types of performance measurements generatedbased at least in part on cumulative suspend time of the truck thread224-1 using the techniques disclosed herein, such a performancemeasurement is highly accurate.

The disclosed techniques therefore provide significant advantages overconventional approaches in which measurements can be inaccurate due to afailure to properly account for periods of time in which a truck threadis suspended in order to allow threads of one or more other applicationsto execute on the same processing core.

It is assumed that each of the other truck threads 224 of processingdevice 108-i operates in the manner described above for truck thread224-1. It is further assumed that each of the other processing devices108 of the storage system 105 is configured in a manner similar to thatillustrated in FIG. 2 for processing device 108-i.

In some embodiments, each of the processing devices 108 incudes its ownsystem manager 216 and performance monitor 218. However, in otherembodiments, it is possible that such components are implemented on onlyone of the processing devices 108, or on other subsets of the processingdevices 108, in which case a system manager 216 and performance monitor218 implemented on one of the processing devices 108 may provide similarsystem management and performance monitoring functionality for one ormore other ones of the processing devices 108. It is therefore possiblethat one or more of the processing devices 108 may not include its owninstances of system manager 216 and/or performance monitor 218. Also,although system manager 216 and performance monitor 218 areillustratively shown as executing on a separate core 210-0 in thisembodiment, this is by way of example only, and in other embodiments,one or more of these components may each be distributed over multipleones of the cores 210.

In some embodiments, storage system 105 may comprise a separateprocessing device that executes the system manager 216 and manages thetruck threads 224 executing on the cores 210 of the processing devices108 of the nodes 106.

Accordingly, in some embodiments, the execution and implementation ofsystem manager 216 and/or performance monitor 218 may be distributedacross multiple cores 210, processing devices 108, and/or nodes 106.

In some embodiments, the system manager 216 and performance monitor 218collectively monitor the core utilization of one or more of theprocessing devices 108 and may dynamically control and change the modesin which the truck threads 224 and other application threads 226 operatein order to adapt the storage system 105 to actual usage patterns of theusers associated with the host devices 102.

These and other embodiments can utilize various techniques for disablingand re-enabling threads, including those disclosed in U.S. patentapplication Ser. No. 16/162,471, filed Oct. 17, 2018 and entitled“Dynamic Multitasking for Distributed Storage Systems,” which isincorporated by reference herein in its entirety.

The operation of the information processing system 100 will now bedescribed in further detail with reference to the flow diagrams of theillustrative embodiments of FIGS. 3A and 3B. The process as shown inFIG. 3A includes steps 300 through 314 and the process as shown in FIG.3B includes steps 350 through 362. The processes shown in FIGS. 3A and3B are suitable for use in system 100 but are more generally applicableto other types of information processing systems in which a storagesystem is configured to implement core thread performance monitoringfunctionality of the type disclosed herein.

The steps of FIGS. 3A and 3B are illustratively performed at least inpart under the control of one or more processing devices 108 of one ormore nodes 106 in storage system 105 of system 100. For example, in someembodiments, the steps of FIGS. 3A and 3B may be performed under thecontrol of system manager 216 executing on processing device 108-i of acorresponding one of the nodes 106 of the storage system 105. Some orall of the steps may be performed asynchronously relative to one anotherrather than serially as illustrated in the figures. Also, multipleinstances of the process can be performed at least in part in parallelto one another for different truck threads or other block-storagethreads of different processing cores of processing device 108-i. It isfurther assumed that each of the other processing devices 108 executessimilar processes for generating performance measurements based oncumulative suspend times maintained for respective truck threads 224 oftheir respective processing cores 210.

Referring initially to FIG. 3A, an example process is shown formaintaining a cumulative suspend time for a given truck thread executingon a particular processing core of a processing device of a node of astorage system. The truck thread in this embodiment is also referred toas a block-storage thread, and is assumed to execute a portion of ablock-storage application of the storage system on the particularprocessing core.

In step 300, the block-storage thread and its X-threads execute on afirst processing core. For example, the block-storage thread maycomprise truck thread 224-1 having X-threads 225-1 executing onprocessing core 210-1 in the FIG. 2 embodiment.

In step 302, a determination is made as to whether or not theblock-storage thread is to be suspended at a particular switch betweentwo of its X-threads. If the block-storage thread will not be suspendedat the particular switch between the X-threads, the process moves tostep 304, and otherwise moves to step 306.

In step 304, the block-storage thread continues to schedule itsX-threads for execution on the first core, and the process returns tostep 300 as indicated. The scheduling of X-threads of the block-storagethread is illustratively performed by its internal scheduler, such asinternal scheduler 230-1 in truck thread 224-1.

In step 306, which is reached if the block-storage thread is to besuspended in conjunction with the current switch between X-threads, theblock-storage thread takes a first timestamp to indicate start of thesuspension, and then suspends itself as indicated, after which theprocess moves to step 308.

In step 308, a file-storage thread is executed on the first core whilethe block-storage thread is suspended on that core. For example, thefile-storage thread may comprise one of the other application threads226-1 that is executed responsive to suspension of the truck thread224-1 under the control of its external scheduler 232-1.

In step 310, a determination is made as to whether or not theblock-storage thread is to be resumed. Such a determination in thepresent embodiment is illustratively made by a waker component ofanother block-storage thread executing on a different one of theprocessing cores of the same processing device. If the suspendedblock-storage thread is to be resumed, the process moves to step 312,and otherwise returns to step 308 to continue executing the file-storagethread on the first core.

In step 312, which is reached if the suspended block-storage thread isto be resumed, the waker component of the block-storage thread executingon the different processing core suspends the file-storage thread on thefirst core, and resumes the previously-suspended block storage thread onthe first core. The process then moves to step 314 as indicated.

In step 314, the resumed block-storage thread on the first core takes asecond timestamp to indicate the end of its suspension, updates thecumulative suspend time (“CST”) using the first and second timestampsthat indicate the respective start and end of its suspension, and storesthe current CST indexed by a current suspension count. Prior to aninitial suspension of the block-storage thread executing on the firstcore, the CST is illustratively initialized to a particular value, suchas zero. The storing of the current CST value indexed by a currentsuspension count illustratively uses a look-up table or other datastructure stored in a memory of the first core on which the resumedblock-storage thread is executing. The data structure in someembodiments comprises a plurality of entries, with each such entrycomprising a different count value and a corresponding CST value that isindexed by its corresponding count value. The process then returns tostep 300 via step 304 as indicated, to continue execution of thenow-resumed block-storage thread and its corresponding X-threads on thefirst core.

Steps 302 through 314 are illustratively repeated for one or moreadditional suspensions of the block-storage thread on the first core,each illustratively performed in order to allow the file-storage threadto execute during the suspension. Thus, the CST of the block-storagethread in this embodiment is maintained over multiple suspensions ofthat block-storage thread, each allowing execution of a different threadon the same core. The above-noted suspension count is incremented witheach such suspension of the block-storage thread. Different suspensioncounts are therefore maintained for respective different block-storagethreads that are subject to suspension in the storage system. Suchincrementing of suspension counts is illustrative performed byrespective external schedulers of the block-storage threads. Forexample, a processing core release component of an external scheduler232-1 of truck thread 224-1 illustratively performs such incrementing,in conjunction with its updating of the CST using the first and secondtimestamps in step 314 of FIG. 3A. The CST for a given truck thread canbe reinitialized to zero under various conditions, such as terminationof that truck thread, possibly occurring in conjunction with a reboot orreconfiguration of the processing device 108-i.

With reference now to FIG. 3B, an example process is shown forgenerating performance measurements, based at least in part on thecumulative suspend time maintained utilizing the process of FIG. 3A.

In step 350, the block-storage thread and its X-threads execute on thefirst processing core, as in step 300 of the process of FIG. 3A.

In step 352, a determination is made as to whether or not a performancemeasurement is to be taken for a given one of the X-threads of theblock-storage thread. If a performance measurement will not be taken forthe given X-thread, the process moves to step 354, and otherwise movesto step 356.

In step 354, the block-storage thread continues to schedule itsX-threads for execution on the first core, and the process returns tostep 350 as indicated. Again, the scheduling of X-threads of theblock-storage thread is illustratively performed by its internalscheduler, such as internal scheduler 230-1 in truck thread 224-1.

In step 356, a first timestamp is taken to indicate the start of aperformance interval and stored with a starting value of the suspensioncount. The performance interval is a period of time for which aperformance measurement is to be taken.

In step 358, a second timestamp is taken to indicate the end of theperformance interval and stored with an ending value of the suspensioncount. It should be noted that the first and second timestamps referredto in respective steps 356 and 358 in the context of a performanceinterval for generating a performance measurement in FIG. 3B aredistinct from the first and second timestamps used to denote start andend of a given suspension of a block-storage thread in FIG. 3A.

In step 360, the starting and ending values of the suspension count areutilized to look up respective corresponding CST values in the datastructure referred to in the context of step 314 of the process of FIG.3A.

In step 362, an adjusted interval duration is computed for theperformance measurement by subtracting, from a difference of the firstand second timestamps, the difference between the CST values determinedin step 360. In this manner, a performance measurement can be generatedfor a given X-thread of the block-storage thread executing on the firstcore based at least in part on the CST of the block-storage thread. Theprocess then returns to step 350 as indicated. In other embodiments, thereturn could be via step 354.

Steps 352 through 362 are illustratively repeated to generateperformance measurements for one or more other X-threads of theblock-storage thread. Such measurements can be performed at least inpart by the external scheduler 232-1 of truck thread 224-1, and moreparticularly at least in part by a processing core release component ofthe external scheduler 232-1, although numerous other arrangements arepossible.

Functionality such as that described in conjunction with the flowdiagrams of FIGS. 3A and 3B can be implemented at least in part in theform of one or more software programs stored in memory and executed by aprocessor of a processing device such as a computer or server. As willbe described below, a memory or other storage device having executableprogram code of one or more software programs embodied therein is anexample of what is more generally referred to herein as a“processor-readable storage medium.”

For example, a storage controller comprising at least a portion of eachof one or more of the processing devices 108 of storage system 105 andconfigured to control performance of one or more steps of the processesof FIGS. 3A and 3B in system 100 can be implemented as part of what ismore generally referred to herein as a processing platform comprisingone or more processing devices each comprising a processor coupled to amemory. A given such storage controller may correspond to one or morevirtual machines or other types of virtualization infrastructure such asDocker containers or Linux containers (LXCs). The storage controller, aswell as other system components, may be implemented at least in partusing processing devices of such processing platforms. For example, in adistributed implementation, respective distributed modules of such astorage system 105 can be implemented in respective containers runningon respective ones of the processing devices of a processing platform.

Additional illustrative embodiments implementing core thread performancemonitoring functionality will now be described with reference to FIGS. 4and 5.

Referring now to FIG. 4, two different example sets of pseudocode 400and 402 are shown, and are associated with respective internal andexternal schedulers of a core thread. For example, the pseudocode 400 isillustratively part of an internal scheduler 230-1 of truck thread224-1, and controls switch points between X-threads 225-1. Moreparticularly, pseudocode 400 is illustratively executed at a givenswitch point between two of the X-threads 225-1, and initially triggersa cycle of the external scheduler 232-1, prior to determining the nextX-thread to execute and scheduling execution of that X-thread.

Pseudocode 402 is illustratively part of the external scheduler 232-1 oftruck thread 224-1, and implements the external scheduler cycletriggered by the pseudocode 400 at the switch point between theX-threads of the truck thread 224-1. In this example external schedulercycle, a processing core release component of the external scheduler232-1, more particularly referred to as a CPU release component,determines if the CPU should be released, and if so takes a firsttimestamp indicative of the start of the suspension, and suspends thetruck thread 224-1 by releasing the CPU. After the truck thread 224-1 isresumed, the external scheduler cycle takes a second timestamp toindicate the end of the suspension, updates the CST using the first andsecond timestamps, and stores the current CST indexed by the currentsuspension count. It also increments the suspension count as shown,although it is to be appreciated that other suspension count maintenancearrangements can be used in other embodiments. For example, theincrementing of the suspension count can occur at a different point inthe external scheduler cycle than that shown in FIG. 4.

Turning now to FIG. 5, a performance monitoring example involvingblock-storage and file-storage applications running on a processing coreis shown. The top portion of the figure illustrates the cumulativesuspend time or CST for this example, as maintained in the mannerdescribed above, over multiple suspensions of a block-storage thread ona given processing core to allow a file-storage thread to execute onthat same core. The remaining portion of the figure includes a timelinethat shows the suspensions of the block-storage thread, illustrativelyfive suspensions for respective durations of 50 microseconds (“us”), 40us, 100 us, 70 us and 50 us. The CST that is illustratively maintainedby an external scheduler of the block-storage thread over these multiplesuspensions of the block-storage thread thus increases from an initialsuspension duration of 50 us, to 50 us+40 us=90 us, to 90 us+100 us=190us, to 190 us+70 us=260 us, and finally to 260 us+50 us=310 us, asillustrated. The CST is assumed to be initialized to zero at some pointprior to the first suspension of the block-storage thread, and asindicated previously herein may eventually be reinitialized to zerounder certain conditions.

In the present embodiment, the CST of the block-storage thread is savedeach time that the block-storage thread resumes after a previoussuspension. For example, when the external scheduler decides to releasethe processing core, it will take a timestamp (T1) to indicate the startof the suspension, and when the block-storage thread resumes, it willtake another timestamp (T2), add the interval T2-T1 to the CST, and savethe updated CST. The external scheduler also stores the current numberof suspensions (denoted “NumSuspends”). The CST values that are savedfor every suspend event are indexed by the corresponding values of thesuspension count, for example, in a look-up table or other datastructure. In addition, whenever an X-thread performance monitoringcomponent takes starting and ending timestamps (denoted “StartTimestamp”and “EndTimestamp”) of an interval it wants to measure, that componentwill also save the respective corresponding current values ofNumSuspends (denoted “StartNumSuspends” and “EndNumSuspends”). When theinterval finishes, the correct time duration can be obtained by thefollowing low-complexity calculation, which computes an actual intervalduration (denoted “IntervalDuration”) from a gross measurement of theinterval duration (denoted “IntervalDurationGross”):

IntervalDuration=IntervalDurationGross−(CST[EndNumSuspends]−CST[StartNumSuspends])

where:

CST[EndNumSuspends]=CST value after EndNumSuspends, and

CST[StartNumSuspends]=CST value after StartNumSuspends.

With reference again to the example in the figure, it can be seen thatthe gross measurement for the gross interval duration indicated by thelength of the horizontal arrow is adjusted to subtract therefrom theamount of CST accumulated over the second to fifth suspensions, denotedin the figure as CST[4]−CST[0]=310 us-50 us=260 us.

The FIG. 5 embodiment and other illustrative embodiments herein providea mechanism that enables accurate measurements of time intervals offlows of a storage system, taking into account context switches and runtime of other applications.

More particularly, in the FIG. 5 embodiment, the storage system isconfigured to maintain information about the time durations ofrespective multiple suspensions of the truck thread, in a way thatpermits calculation of the relevant suspend durations that occurredduring every interval measured by an X-thread performance monitoringmechanism. These durations can be subtracted from a gross measurement ofthe desired interval, in order to obtain the correct value of theinterval duration. Such measured time intervals are examples of what aremore generally referred to herein as “performance measures.” It is to beappreciated that the particular features of FIGS. 4 and 5, and those ofother illustrative embodiments, are presented by way of example only,and should not be construed as limiting in any way.

In some embodiments, a storage system comprises a distributed contentaddressable storage (CAS) system configured to support performancemonitoring functionality for core threads having internal and externalschedulers as disclosed herein. A distributed CAS system is alsoreferred to herein as a clustered CAS system. A “distributed CAS system”as that term is broadly used herein includes any CAS system that isdistributed across multiple storage nodes, such as the nodes 106 ofstorage system 105.

An illustrative embodiment of such a CAS system will now be describedwith reference to FIG. 6. In this embodiment, a CAS system 605 comprisesa plurality of storage devices 606 and an associated storage controller608. The CAS system 605 may be viewed as a particular implementation ofthe storage system 105, and accordingly is assumed to be coupled to hostdevices 102 via network 104 in system 100.

The storage controller 608 in the present embodiment is configured tosupport storage system core thread performance monitoring functionalityof the type previously described in conjunction with FIGS. 1 through 5.For example, the CAS system 605 illustratively interacts with one ormore host devices 102 to support performance of a process such as thatshown in FIG. 3, in order to implement performance monitoringfunctionality for core threads executing in the CAS system 605.

The storage controller 608 includes distributed modules 616 and 618,which are configured to operate in a manner similar to that describedabove for respective system manager 216 and performance monitor 218 ofthe processing device 108-i of system 100. Module 616 is moreparticularly referred to as distributed system management logic, andillustratively comprises multiple system management logic instances onrespective ones of a plurality of distinct nodes, with the multiplesystem management logic instances collectively supporting core threadperformance monitoring functionality as disclosed herein. Module 618more particularly comprises distributed performance monitoring logicwith different instances thereof also being implemented on respectiveones of the distinct nodes.

The CAS system 605 in the FIG. 6 embodiment is implemented as adistributed storage system and illustratively includes a plurality ofstorage nodes 615 each comprising a corresponding subset of the storagedevices 606. Such storage nodes 615 are examples of the “distinct nodes”referred to above, and other distributed or clustered storage systemarrangements comprising multiple storage nodes and possibly additionalor alternative nodes can be used in other embodiments. A givendistributed or clustered storage system may therefore include not onlystorage nodes 615 but also additional storage nodes, compute nodes orother types of nodes coupled to network 104. Alternatively, suchadditional storage nodes may be part of another distributed or clusteredstorage system of the system 100. Each of the storage nodes 615 of theCAS system 605 is assumed to be implemented using at least oneprocessing device comprising a processor coupled to a memory.

The storage controller 608 of the CAS system 605 is implemented in adistributed manner so as to comprise a plurality of distributed storagecontroller components implemented on respective ones of the storagenodes 615. The storage controller 608 is therefore an example of what ismore generally referred to herein as a “distributed storage controller.”In subsequent description herein, the storage controller 608 is referredto as distributed storage controller 608.

Each of the storage nodes 615 in this embodiment further comprises a setof processing modules configured to communicate over one or morenetworks with corresponding sets of processing modules on other ones ofthe storage nodes 615. The sets of processing modules of the storagenodes 615 collectively comprise at least a portion of the distributedstorage controller 608 of the CAS system 605.

The modules of the distributed storage controller 608 in the presentembodiment more particularly comprise different sets of processingmodules implemented on each of the storage nodes 615. The set ofprocessing modules of each of the storage nodes 615 comprises at least acontrol module 608C, a data module 608D and a routing module 608R. Thedistributed storage controller 608 further comprises one or moremanagement (“MGMT”) modules 608M. For example, only a single one of thestorage nodes 615 may include a management module 608M. It is alsopossible that management modules 608M may be implemented on each of atleast a subset of the storage nodes 615. A given set of processingmodules implemented on a particular one of the storage nodes 615therefore illustratively includes at least one control module 608C, atleast one data module 608D and at least one routing module 608R, andpossibly a management module 608M.

Communication links may be established between the various processingmodules of the distributed storage controller 608 using well-knowncommunication protocols such as TCP/IP and RDMA. For example, respectivesets of IP links used in data transfer and corresponding messaging couldbe associated with respective different ones of the routing modules608R.

Although shown as separate modules of the distributed storage controller608, the modules 616 and 618 in the present embodiment are assumed to bedistributed at least in part over at least a subset of the other modules608C, 608D, 608R and 608M of the storage controller 608.

Accordingly, at least portions of the storage system core threadperformance monitoring functionality of the modules 616 and 618 may beimplemented in one or more of the other modules of the storagecontroller 608. In other embodiments, the modules 616 and 618 may beimplemented as stand-alone modules of the storage controller 608.

The storage devices 606 are configured to store metadata pages 620 anduser data pages 622, and may also store additional information notexplicitly shown such as checkpoints and write journals. The metadatapages 620 and the user data pages 622 are illustratively stored inrespective designated metadata and user data areas of the storagedevices 606. Accordingly, metadata pages 620 and user data pages 622 maybe viewed as corresponding to respective designated metadata and userdata areas of the storage devices 606.

A given “page” as the term is broadly used herein should not be viewedas being limited to any particular range of fixed sizes. In someembodiments, a page size of 8 kilobytes (KB) is used, but this is by wayof example only and can be varied in other embodiments. For example,page sizes of 4 KB, 16 KB or other values can be used. Accordingly,illustrative embodiments can utilize any of a wide variety ofalternative paging arrangements for organizing the metadata pages 620and the user data pages 622.

The user data pages 622 are part of a plurality of LUNs configured tostore files, blocks, objects or other arrangements of data, each alsogenerally referred to herein as a “data item,” on behalf of users of theCAS system 605. Each such LUN may comprise particular ones of theabove-noted pages of the user data area. The user data stored in theuser data pages 622 can include any type of user data that may beutilized in the system 100. The term “user data” herein is thereforealso intended to be broadly construed.

A given storage volume for which content-based signatures are generatedin the CAS system 605 illustratively comprises a set of one or moreLUNs, each including multiple ones of the user data pages 622 stored instorage devices 606.

The CAS system 605 in the embodiment of FIG. 6 is configured to generatehash metadata providing a mapping between content-based digests ofrespective ones of the user data pages 622 and corresponding physicallocations of those pages in the user data area. Content-based digestsgenerated using hash functions are also referred to herein as “hashdigests.” Such hash digests or other types of content-based digests areexamples of what are more generally referred to herein as “content-basedsignatures” of the respective user data pages 622. The hash metadatagenerated by the CAS system 605 is illustratively stored as metadatapages 620 in the metadata area. The generation and storage of the hashmetadata is assumed to be performed under the control of the storagecontroller 608.

Each of the metadata pages 620 characterizes a plurality of the userdata pages 622. For example, in a given set of n user data pagesrepresenting a portion of the user data pages 622, each of the user datapages is characterized by a LUN identifier, an offset and acontent-based signature.

The content-based signature is generated as a hash function of contentof the corresponding user data page. Illustrative hash functions thatmay be used to generate the content-based signature include thewell-known SHA1 secure hashing algorithm, or other secure hashingalgorithms known to those skilled in the art, including SHA2, SHA256 andmany others. The content-based signature is utilized to determine thelocation of the corresponding user data page within the user data areaof the storage devices 606.

Each of the metadata pages 620 in the present embodiment is assumed tohave a signature that is not content-based. For example, the metadatapage signatures may be generated using hash functions or other signaturegeneration algorithms that do not utilize content of the metadata pagesas input to the signature generation algorithm. Also, each of themetadata pages is assumed to characterize a different set of the userdata pages.

A given set of metadata pages representing a portion of the metadatapages 620 in an illustrative embodiment comprises metadata pages havingrespective signatures. Each such metadata page characterizes a differentset of n user data pages. For example, the characterizing information ineach metadata page can include the LUN identifiers, offsets andcontent-based signatures for each of the n user data pages that arecharacterized by that metadata page. It is to be appreciated, however,that the user data and metadata page configurations described above areexamples only, and numerous alternative user data and metadata pageconfigurations can be used in other embodiments.

Ownership of a user data logical address space within the CAS system 605is illustratively distributed among the control modules 608C.

The storage system core thread performance monitoring functionalityprovided at least in part by modules 616 and 618 in this embodiment isassumed to be distributed across multiple distributed processingmodules, including at least a subset of the processing modules 608C,608D, 608R and 608M of the distributed storage controller 608.

For example, the management module 608M of the storage controller 608may include a system management logic instance that engagescorresponding system management logic instances in all of the controlmodules 608C and routing modules 608R in order to support storage systemcore thread performance monitoring functionality of the CAS system 605.

In some embodiments, each user data page has a fixed size such as 8 KBand its content-based signature is a 20-byte signature generated usingthe SHA1 secure hashing algorithm. Also, each page has a LUN identifierand an offset, and so is characterized by <lun_id, offset, signature>.

The content-based signature in the present example comprises acontent-based digest of the corresponding data page. Such acontent-based digest is more particularly referred to as a “hash digest”of the corresponding data page, as the content-based signature isillustratively generated by applying a hash function such as the SHA1secure hashing algorithm to the content of that data page. The full hashdigest of a given data page is given by the above-noted 20-bytesignature. The hash digest may be represented by a corresponding “hashhandle,” which in some cases may comprise a particular portion of thehash digest. The hash handle illustratively maps on a one-to-one basisto the corresponding full hash digest within a designated clusterboundary or other specified storage resource boundary of a given storagesystem. In arrangements of this type, the hash handle provides alightweight mechanism for uniquely identifying the corresponding fullhash digest and its associated data page within the specified storageresource boundary. The hash digest and hash handle are both consideredexamples of “content-based signatures” as that term is broadly usedherein.

Examples of techniques for generating and processing hash handles forrespective hash digests of respective data pages are disclosed in U.S.Pat. No. 9,208,162, entitled “Generating a Short Hash Handle,” and U.S.Pat. No. 9,286,003, entitled “Method and Apparatus for Creating a ShortHash Handle Highly Correlated with a Globally-Unique Hash Signature,”both of which are incorporated by reference herein.

The distributed storage controller 608 in this example is configured togroup consecutive pages into page groups, to arrange the page groupsinto slices, and to assign the slices to different ones of the controlmodules 608C. For example, if there are 1024 slices distributed evenlyacross the control modules 608C, and there are a total of 16 controlmodules in a given implementation, each of the control modules “owns”1024/16=64 slices. In such arrangements, different ones of the slicesare assigned to different ones of the control modules 608C such thatcontrol of the slices within the storage controller 608 of the CASsystem 605 is substantially evenly distributed over the control modules608C of the distributed storage controller 608.

The data modules 608D allow a user to locate a given user data pagebased on its signature. Each metadata page also has a size of 8 KB andincludes multiple instances of the <lun_id, offset, signature> forrespective ones of a plurality of the user data pages. Such metadatapages are illustratively generated by the control modules 608C but areaccessed using the data modules 608D based on a metadata page signature.

The metadata page signature in this embodiment is a 20-byte signaturebut is not based on the content of the metadata page. Instead, themetadata page signature is generated based on an 8-byte metadata pageidentifier that is a function of the LUN identifier and offsetinformation of that metadata page.

If a user wants to read a user data page having a particular LUNidentifier and offset, the corresponding metadata page identifier isfirst determined, then the metadata page signature is computed for theidentified metadata page, and then the metadata page is read using thecomputed signature. In this embodiment, the metadata page signature ismore particularly computed using a signature generation algorithm thatgenerates the signature to include a hash of the 8-byte metadata pageidentifier, one or more ASCII codes for particular predeterminedcharacters, as well as possible additional fields. The last bit of themetadata page signature may always be set to a particular logic value soas to distinguish it from the user data page signature in which the lastbit may always be set to the opposite logic value.

The metadata page signature is used to retrieve the metadata page viathe data module. This metadata page will include the <lun_id, offset,signature> for the user data page if the user page exists. The signatureof the user data page is then used to retrieve that user data page, alsovia the data module.

Write requests processed in the CAS system 605 each illustrativelycomprise one or more IO operations directing that at least one data itemof the CAS system 605 be written to in a particular manner. A givenwrite request is illustratively received in the CAS system 605 from ahost device over a network. In some embodiments, a write request isreceived in the distributed storage controller 608 of the CAS system605, and directed from one processing module to another processingmodule of the distributed storage controller 608. For example, areceived write request may be directed from a routing module 608R of thedistributed storage controller 608 to a particular control module 608Cof the distributed storage controller 608. Other arrangements forreceiving and processing write requests from one or more host devicescan be used.

The term “write request” as used herein is intended to be broadlyconstrued, so as to encompass one or more IO operations directing thatat least one data item of a storage system be written to in a particularmanner. A given write request is illustratively received in a storagesystem from a host device.

In some embodiments, the control modules 608C, data modules 608D androuting modules 608R of the storage nodes 615 communicate with oneanother over a high-speed internal network such as an InfiniBandnetwork. The control modules 608C, data modules 608D and routing modules608R coordinate with one another to accomplish various IO processingtasks.

The write requests from the host devices identify particular data pagesto be written in the CAS system 605 by their corresponding logicaladdresses each comprising a LUN ID and an offset.

As noted above, a given one of the content-based signaturesillustratively comprises a hash digest of the corresponding data page,with the hash digest being generated by applying a hash function to thecontent of that data page. The hash digest may be uniquely representedwithin a given storage resource boundary by a corresponding hash handle.

The processing modules of distributed storage controller 608 asdisclosed herein utilize metadata structures that include logical layerand physical layer mapping tables to be described below. It is to beappreciated that these particular tables are only examples, and othertables or metadata structures having different configurations of entriesand fields can be used in other embodiments. The logical layer andphysical layer mapping tables in this embodiment illustratively includethe following:

1. An address-to-hash (“A2H”) table. The A2H table comprises a pluralityof entries accessible utilizing logical addresses as respective keys,with each such entry of the A2H table comprising a corresponding one ofthe logical addresses, a corresponding one of the hash handles, andpossibly one or more additional fields.

2. A hash-to-data (“H2D”) table that illustratively comprises aplurality of entries accessible utilizing hash handles as respectivekeys, with each such entry of the H2D table comprising a correspondingone of the hash handles, a physical offset of a corresponding one of thedata pages, and possibly one or more additional fields.

3. A hash metadata (“HMD”) table illustratively comprising a pluralityof entries accessible utilizing hash handles as respective keys. Eachsuch entry of the HMD table comprises a corresponding one of the hashhandles, a corresponding reference count and a corresponding physicaloffset of one of the data pages. A given one of the reference countsdenotes the number of logical pages in the storage system that have thesame content as the corresponding data page and therefore point to thatsame data page via their common hash digest. The HMD tableillustratively comprises at least a portion of the same information thatis found in the H2D table. Accordingly, in other embodiments, those twotables can be combined into a single table, illustratively referred toas an H2D table, an HMD table or another type of physical layer mappingtable providing a mapping between hash values, such as hash handles orhash digests, and corresponding physical addresses of data pages.

4. A physical layer based (“PLB”) table that illustratively comprises aplurality of entries accessible utilizing physical offsets as respectivekeys, with each such entry of the PLB table comprising a correspondingone of the physical offsets, a corresponding one of the hash digests,and possibly one or more additional fields.

As indicated above, the hash handles are generally shorter in lengththan the corresponding hash digests of the respective data pages, andeach illustratively provides a short representation of the correspondingfull hash digest. For example, in some embodiments, the full hashdigests are 20 bytes in length, and their respective corresponding hashhandles are illustratively only 4 or 6 bytes in length.

Again, the logical layer and physical layer mapping tables referred toabove are examples only, and can be varied in other embodiments. Forexample, other types of hash-to-physical (“H2P”) mapping tables may beused in addition to or in place of the above-noted HMD and PLB tables.

In some embodiments, certain ones of the above-described mapping tablesare maintained by particular modules of distributed storage controller608. For example, the mapping tables maintained by the control modules608C illustratively comprise at least one A2H table and possibly also atleast one H2D table. The A2H tables are utilized to storeaddress-to-hash mapping information and the H2D tables are utilized tostore hash-to-data mapping information, in support of mapping of logicaladdresses for respective pages to corresponding physical addresses forthose pages via respective hashes or other types of content-basedsignatures, as described in further detail elsewhere herein.

The CAS system 605 utilizes a two-level mapping process to map logicalblock addresses to physical block addresses. The first level of mappinguses an A2H table and the second level of mapping uses an HMD table,with the A2H and HMD tables corresponding to respective logical andphysical layers of the content-based signature mapping within the CASsystem 605. The HMD table or a given portion thereof in some embodimentsdisclosed herein is more particularly referred to as an H2D table,although it is to be understood that these and other mapping tables orother data structures referred to herein can be varied in otherembodiments.

The first level of mapping using the A2H table associates logicaladdresses of respective data pages with respective content-basedsignatures of those data pages. This is also referred to as logicallayer mapping.

The second level of mapping using the HMD table associates respectiveones of the content-based signatures with respective physical storagelocations in one or more of the storage devices 606. This is alsoreferred to as physical layer mapping.

Examples of these and other metadata structures utilized in illustrativeembodiments were described above. These particular examplesillustratively include respective A2H, H2D, HMD and PLB tables. In someembodiments, the A2H and H2D tables are utilized primarily by thecontrol modules 608C, while the HMD and PLB tables are utilizedprimarily by the data modules 608D.

For a given write request, hash metadata comprising at least a subset ofthe above-noted tables is updated in conjunction with the processing ofthat write request.

The A2H, H2D, HMD and PLB tables described above are examples of whatare more generally referred to herein as “mapping tables” of respectivedistinct types. Other types and arrangements of mapping tables or othercontent-based signature mapping information may be used in otherembodiments.

Such mapping tables are still more generally referred to herein as“metadata structures” of the CAS system 605. It should be noted thatadditional or alternative metadata structures can be used in otherembodiments. References herein to particular tables of particular types,such as A2H, H2D, HMD and PLB tables, and their respectiveconfigurations, should be considered non-limiting and are presented byway of illustrative example only. Such metadata structures can beimplemented in numerous alternative configurations with differentarrangements of fields and entries in other embodiments.

The logical block addresses or LBAs of a logical layer of the CAS system605 correspond to respective physical blocks of a physical layer of theCAS system 605. The user data pages of the logical layer are organizedby LBA and have reference via respective content-based signatures toparticular physical blocks of the physical layer.

Each of the physical blocks has an associated reference count that ismaintained within the CAS system 605. The reference count for a givenphysical block indicates the number of logical blocks that point to thatsame physical block.

In releasing logical address space in the storage system, adereferencing operation is generally executed for each of the LBAs beingreleased. More particularly, the reference count of the correspondingphysical block is decremented. A reference count of zero indicates thatthere are no longer any logical blocks that reference the correspondingphysical block, and so that physical block can be released.

It should also be understood that the particular arrangement of storagecontroller processing modules 608C, 608D, 608R and 608M as shown in theFIG. 6 embodiment is presented by way of example only. Numerousalternative arrangements of processing modules of a distributed storagecontroller may be used to implement performance monitoring functionalityfor core threads of a distributed storage system in other embodiments.

Additional examples of content addressable storage functionalityimplemented in some embodiments by control modules 608C, data modules608D, routing modules 608R and management module(s) 608M of distributedstorage controller 608 can be found in U.S. Pat. No. 9,104,326, entitled“Scalable Block Data Storage Using Content Addressing,” which isincorporated by reference herein. Alternative arrangements of these andother storage node processing modules of a distributed storagecontroller in a CAS system can be used in other embodiments.

Illustrative embodiments of a storage system with performance monitoringfunctionality for storage system core threads with internal and externalschedulers as disclosed herein can provide a number of significantadvantages relative to conventional arrangements.

For example, illustrative embodiments disclosed herein areadvantageously configured to provide substantially improved performancemeasurement accuracy in situations in which a given processing core of astorage system is used to execute multiple threads of respectivedifferent applications.

More particularly, some embodiments are configured to generate highlyaccurate performance measurements for respective sub-threads of a giventhread of a primary storage application executing on a processing core,even in situations in which that thread is repeatedly suspended in orderto allow one or more threads of one or more other applications toexecute on the same processing core.

These and other embodiments thereby avoid the inaccurate measurementsand other drawbacks of conventional core thread performance monitoringapproaches, which have difficulty in situations where a given processingcore is used to execute multiple threads of different applications.

Moreover, storage system core thread performance monitoringfunctionality in illustrative embodiments herein does not adverselyimpact the performance of the storage system in handling IO requests.

It is to be appreciated that the particular advantages described aboveand elsewhere herein are associated with particular illustrativeembodiments and need not be present in other embodiments. Also, theparticular types of information processing system features andfunctionality as illustrated in the drawings and described above areexemplary only, and numerous other arrangements may be used in otherembodiments.

Illustrative embodiments of processing platforms utilized to implementhost devices and/or storage systems incorporating performance monitoringfunctionality for core threads with internal and external schedulerswill now be described in greater detail with reference to FIGS. 7 and 8.

Although described in the context of information processing system 100,these processing platforms may also be used to implement at leastportions of other information processing systems in other embodiments.

FIG. 7 shows an example processing platform comprising cloudinfrastructure 700. The cloud infrastructure 700 comprises a combinationof physical and virtual processing resources that may be utilized toimplement at least a portion of the information processing system 100.The cloud infrastructure 700 comprises multiple virtual machines (VMs)and/or container sets 702-1, 702-2, . . . 702-L implemented usingvirtualization infrastructure 704. The virtualization infrastructure 704runs on physical infrastructure 705, and illustratively comprises one ormore hypervisors and/or operating system level virtualizationinfrastructure. The operating system level virtualization infrastructureillustratively comprises kernel control groups of a Linux operatingsystem or other type of operating system.

The cloud infrastructure 700 further comprises sets of applications710-1, 710-2, . . . 710-L running on respective ones of theVMs/container sets 702-1, 702-2, . . . 702-L under the control of thevirtualization infrastructure 704. The VMs/container sets 702 maycomprise respective VMs, respective sets of one or more containers, orrespective sets of one or more containers running in VMs.

In some implementations of the FIG. 7 embodiment, the VMs/container sets702 comprise respective VMs implemented using virtualizationinfrastructure 704 that comprises at least one hypervisor. Suchimplementations can provide performance monitoring functionality forcore threads of a storage system of the type described above using oneor more processes running on a given one of the VMs. For example, eachof the VMs can implement one or more system management logic instancesand/or performance monitoring logic instances for supporting theabove-described performance management functionality for core threadswith internal and external schedulers in the storage system 105 ofsystem 100.

A hypervisor platform may be used to implement a hypervisor within thevirtualization infrastructure 704. Such a hypervisor platform maycomprise an associated virtual infrastructure management system. Theunderlying physical machines may comprise one or more distributedprocessing platforms that include one or more storage systems.

In other implementations of the FIG. 7 embodiment, the VMs/containersets 702 comprise respective containers implemented using virtualizationinfrastructure 704 that provides operating system level virtualizationfunctionality, such as support for Docker containers running on baremetal hosts, or Docker containers running on VMs. The containers areillustratively implemented using respective kernel control groups of theoperating system. Such implementations can also provide performancemonitoring functionality for core threads of a storage system of thetype described above. For example, a container host device supportingmultiple containers of one or more container sets can implement one ormore system management logic instances and/or performance monitoringlogic instances for supporting the above-described performancemanagement functionality for core threads with internal and externalschedulers in the storage system 105 of system 100.

As is apparent from the above, one or more of the processing modules orother components of system 100 may each run on a computer, server,storage device or other processing platform element. A given suchelement may be viewed as an example of what is more generally referredto herein as a “processing device.” The cloud infrastructure 700 shownin FIG. 7 may represent at least a portion of one processing platform.Another example of such a processing platform is processing platform 800shown in FIG. 8.

The processing platform 800 in this embodiment comprises a portion ofsystem 100 and includes a plurality of processing devices, denoted802-1, 802-2, 802-3, . . . 802-K, which communicate with one anotherover a network 804.

The network 804 may comprise any type of network, including by way ofexample a global computer network such as the Internet, a WAN, a LAN, asatellite network, a telephone or cable network, a cellular network suchas a 4G or 5G network, a wireless network such as a WiFi or WiMAXnetwork, or various portions or combinations of these and other types ofnetworks.

The processing device 802-1 in the processing platform 800 comprises aprocessor 810 coupled to a memory 812.

The processor 810 may comprise a single-core or multi-core CPU, amicroprocessor, a microcontroller, an application-specific integratedcircuit (ASIC), a field-programmable gate array (FPGA), graphicsprocessing unit (GPU) or other type of processing circuitry, as well asportions or combinations of such circuitry elements.

The memory 812 may comprise random access memory (RAM), read-only memory(ROM), flash memory or other types of memory, in any combination. Thememory 812 and other memories disclosed herein should be viewed asillustrative examples of what are more generally referred to as“processor-readable storage media” storing executable program code ofone or more software programs.

Articles of manufacture comprising such processor-readable storage mediaare considered illustrative embodiments. A given such article ofmanufacture may comprise, for example, a storage array, a storage diskor an integrated circuit containing RAM, ROM, flash memory or otherelectronic memory, or any of a wide variety of other types of computerprogram products. The term “article of manufacture” as used hereinshould be understood to exclude transitory, propagating signals.Numerous other types of computer program products comprisingprocessor-readable storage media can be used.

Also included in the processing device 802-1 is network interfacecircuitry 814, which is used to interface the processing device with thenetwork 804 and other system components, and may comprise conventionaltransceivers.

The other processing devices 802 of the processing platform 800 areassumed to be configured in a manner similar to that shown forprocessing device 802-1 in the figure.

Again, the particular processing platform 800 shown in the figure ispresented by way of example only, and system 100 may include additionalor alternative processing platforms, as well as numerous distinctprocessing platforms in any combination, with each such platformcomprising one or more computers, servers, storage devices or otherprocessing devices.

For example, other processing platforms used to implement illustrativeembodiments can comprise converged infrastructure such as VxRail™,VxRack™, VxRack™ FLEX, VxBlock™ or Vblock® converged infrastructure fromDell EMC.

It should therefore be understood that in other embodiments differentarrangements of additional or alternative elements may be used. At leasta subset of these elements may be collectively implemented on a commonprocessing platform, or each such element may be implemented on aseparate processing platform.

As indicated previously, components of an information processing systemas disclosed herein can be implemented at least in part in the form ofone or more software programs stored in memory and executed by aprocessor of a processing device. For example, at least portions of theperformance monitoring functionality for storage system core threadswith internal and external schedulers as disclosed herein areillustratively implemented in the form of software running on one ormore processing devices.

It should again be emphasized that the above-described embodiments arepresented for purposes of illustration only. Many variations and otheralternative embodiments may be used. For example, the disclosedtechniques are applicable to a wide variety of other types ofinformation processing systems, host devices, storage systems, storagenodes, storage devices, storage controllers, processing cores, threads,internal and external schedulers, applications, system management logicinstances, performance monitoring logic instances and other components.Also, the particular configurations of system and device elements andassociated processing operations illustratively shown in the drawingscan be varied in other embodiments. Moreover, the various assumptionsmade above in the course of describing the illustrative embodimentsshould also be viewed as exemplary rather than as requirements orlimitations of the disclosure. Numerous other alternative embodimentswithin the scope of the appended claims will be readily apparent tothose skilled in the art.

What is claimed is:
 1. An apparatus comprising: at least one processingdevice comprising a processor coupled to a memory; said at leastprocessing device being configured: to monitor performance of a firstthread of a first application executing on one of a plurality ofprocessing cores of a storage system; the first thread comprising aninternal scheduler configured to control switching between a pluralityof sub-threads of the first thread, and an external scheduler configuredto control release of the processing core by the first thread for use byat least a second thread of a second application different than thefirst application; in conjunction with monitoring the performance of thefirst thread in executing the first application, to maintain acumulative suspend time of the first thread over multiple suspensions ofthe first thread, one or more of the multiple suspensions allowing atleast the second thread of the second application to execute on theprocessing core; and to generate performance measurements for respectiveones of the sub-threads of the first thread based at least in part onthe cumulative suspend time of the first thread.
 2. The apparatus ofclaim 1 wherein said at least one processing device comprises at least asubset of the plurality of processing cores of the storage system. 3.The apparatus of claim 1 wherein the first application comprises ablock-storage application of the storage system.
 4. The apparatus ofclaim 1 wherein the second application comprises a file-storageapplication of the storage system.
 5. The apparatus of claim 1 whereinthe first thread comprises a truck thread that when executing on theprocessing core is configured to utilize substantially all availableprocessing resources of the processing core.
 6. The apparatus of claim 1wherein the external scheduler of the first thread comprises: aprocessing core release component configured to determine, inconjunction with each switch between sub-threads of the first thread,whether or not the first thread will suspend itself so as to release theprocessing core for use by at least the second thread of the secondapplication; and a waker component configured to determine, inconjunction with each switch between sub-threads of the first thread,whether or not there is at least one additional thread of the firstapplication to be returned from suspension prior to release of theprocessing core by the first thread; the processing core releasecomponent further operating in conjunction with the waker component toreturn the first thread from suspension.
 7. The apparatus of claim 1wherein each of the sub-threads of the first thread is in one ofmultiple designated states at a particular point in time, including arunning state, a ready state and a suspended state.
 8. The apparatus ofclaim 7 wherein the sub-threads comprise respective non-preemptivethreads and the first thread is configured such that no sub-thread inthe running state is suspended to allow release of the processing coreby the first thread for use by the second thread, the multiplesuspensions of the first thread each occurring in conjunction with aswitch between sub-threads of the first thread.
 9. The apparatus ofclaim 7 wherein generating performance measurements for respective onesof the sub-threads of the first thread based at least in part on thecumulative suspend time of the first thread comprises: generating aready time measurement for a particular one of the sub-threads; andadjusting the ready time measurement based at least in part on thecumulative suspend time of the first thread; wherein the adjusted readytime measurement is indicative of an amount of time the sub-thread spentin the ready state while the first thread was not suspended.
 10. Theapparatus of claim 7 wherein generating performance measurements forrespective ones of the sub-threads of the first thread based at least inpart on the cumulative suspend time of the first thread comprises:generating a suspend time measurement for a particular one of thesub-threads; and adjusting the suspend time measurement based at leastin part on the cumulative suspend time of the first thread; wherein theadjusted suspend time measurement is indicative of an amount of time thesub-thread spent in the suspended state while the first thread was notsuspended.
 11. The apparatus of claim 1 wherein maintaining a cumulativesuspend time of the first thread over multiple suspensions of the firstthread comprises, for each of the multiple suspensions of the firstthread: taking a first timestamp to indicate start of the suspension;taking a second timestamp to indicate resumption of the first threadfrom the suspension; and adding a time interval corresponding to adifference between the first and second timestamps to the cumulativesuspend time.
 12. The apparatus of claim 1 wherein maintaining acumulative suspend time of the first thread over multiple suspensions ofthe first thread comprises, for each of the multiple suspensions of thefirst thread, storing a current value of the cumulative suspend time inassociation with a current value of a suspension number counter that isincremented with each of the multiple suspensions of the first thread.13. The apparatus of claim 12 wherein generating performancemeasurements for respective ones of the sub-threads of the first threadbased at least in part on the cumulative suspend time of the firstthread comprises: taking a first timestamp to indicate start of aperformance interval; storing a starting value of the suspension numbercounter in conjunction with taking the first timestamp; taking a secondtimestamp to indicate end of the performance interval; storing an endingvalue of the suspension number counter in conjunction with taking thesecond timestamp; utilizing the starting and ending values of thesuspension number counter to determine respective corresponding valuesof the cumulative suspend time of the first thread; and adjusting adifference between the first and second timestamps based at least inpart on a difference between the corresponding values of the cumulativesuspend time of the first thread.
 14. A method comprising: monitoringperformance of a first thread of a first application executing on one ofa plurality of processing cores of a storage system; the first threadcomprising an internal scheduler configured to control switching betweena plurality of sub-threads of the first thread, and an externalscheduler configured to control release of the processing core by thefirst thread for use by at least a second thread of a second applicationdifferent than the first application; in conjunction with monitoring theperformance of the first thread in executing the first application,maintaining a cumulative suspend time of the first thread over multiplesuspensions of the first thread, one or more of the multiple suspensionsallowing at least the second thread of the second application to executeon the processing core; and generating performance measurements forrespective ones of the sub-threads of the first thread based at least inpart on the cumulative suspend time of the first thread.
 15. The methodof claim 14 wherein maintaining a cumulative suspend time of the firstthread over multiple suspensions of the first thread comprises, for eachof the multiple suspensions of the first thread: taking a firsttimestamp to indicate start of the suspension; taking a second timestampto indicate resumption of the first thread from the suspension; andadding a time interval corresponding to a difference between the firstand second timestamps to the cumulative suspend time.
 16. The method ofclaim 14 wherein maintaining a cumulative suspend time of the firstthread over multiple suspensions of the first thread comprises, for eachof the multiple suspensions of the first thread, storing a current valueof the cumulative suspend time in association with a current value of asuspension number counter that is incremented with each of the multiplesuspensions of the first thread.
 17. The method of claim 16 whereingenerating performance measurements for respective ones of thesub-threads of the first thread based at least in part on the cumulativesuspend time of the first thread comprises: taking a first timestamp toindicate start of a performance interval; storing a starting value ofthe suspension number counter in conjunction with taking the firsttimestamp; taking a second timestamp to indicate end of the performanceinterval; storing an ending value of the suspension number counter inconjunction with taking the second timestamp; utilizing the starting andending values of the suspension number counter to determine respectivecorresponding values of the cumulative suspend time of the first thread;and adjusting a difference between the first and second timestamps basedat least in part on a difference between the corresponding values of thecumulative suspend time of the first thread.
 18. A computer programproduct comprising a non-transitory processor-readable storage mediumhaving stored therein program code of one or more software programs,wherein the program code when executed by at least one processing devicecomprising a processor coupled to a memory, causes said at least oneprocessing device: to monitor performance of a first thread of a firstapplication executing on one of a plurality of processing cores of astorage system; the first thread comprising an internal schedulerconfigured to control switching between a plurality of sub-threads ofthe first thread, and an external scheduler configured to controlrelease of the processing core by the first thread for use by at least asecond thread of a second application different than the firstapplication; in conjunction with monitoring the performance of the firstthread in executing the first application, to maintain a cumulativesuspend time of the first thread over multiple suspensions of the firstthread, one or more of the multiple suspensions allowing at least thesecond thread of the second application to execute on the processingcore; and to generate performance measurements for respective ones ofthe sub-threads of the first thread based at least in part on thecumulative suspend time of the first thread.
 19. The computer programproduct of claim 18 wherein maintaining a cumulative suspend time of thefirst thread over multiple suspensions of the first thread comprises,for each of the multiple suspensions of the first thread: taking a firsttimestamp to indicate start of the suspension; taking a second timestampto indicate resumption of the first thread from the suspension; andadding a time interval corresponding to a difference between the firstand second timestamps to the cumulative suspend time.
 20. The computerprogram product of claim 18 wherein maintaining a cumulative suspendtime of the first thread over multiple suspensions of the first threadcomprises, for each of the multiple suspensions of the first thread,storing a current value of the cumulative suspend time in associationwith a current value of a suspension number counter that is incrementedwith each of the multiple suspensions of the first thread.